Method and apparatus for facilitating frictionless two-factor authentication

ABSTRACT

A method, apparatus and computer program products are provided for facilitating performing frictionless two-factor authentication. One example method includes receiving, from a first entity, an indication of a request, received at the first entity, to access an account from a device associated with a user, the indication comprising at least one instance of first device identification information of at least one device having authorization to access the account, receiving, from a second entity, second device identification information, the second device identification information determined upon the device accessing to the network address, performing a real-time comparison between the first device identification information and second device identification information, and prompting the first entity to grant the device access to the account if a match is detected between the first device identification information and second device identification information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.62/290,491, filed Feb. 3, 2016, U.S. Provisional Application No.62/313,845, filed Mar. 28, 2016, U.S. Provisional Application No.62/325,478, filed Apr. 21, 2016, and U.S. Provisional Application No.62/416,210, filed Nov. 2, 2016, the entire contents of each of which areincorporated herein by reference.

TECHNOLOGICAL FIELD

Embodiments described herein generally relate to frictionless two-factorauthentication. In particular, embodiments described herein relate toproviding authentication of access while reducing user input and,specifically to a method, apparatus, and computer program product forreceiving device identification information from both a secured systemindicating devices with authorization and from a network providerindicating the device attempting to access the secured system.

BACKGROUND

While conventional two-factor authentication does provide someheightened security with regard to standard login processes, it has yetto be widely adopted, in part, due to the inconvenience caused to theuser.

In this regard, areas for improving known, existing and/or conventionalauthentication systems have been identified. Through applied effort,ingenuity, and innovation, solutions to improve such systems have beenrealized and are described in connection with embodiments of the presentinvention.

Overview

With IoT (the internet of things), hackers now have access to ourphysical world, and without adequate security/authentication, are ableto unlock others' locks, commandeer their cars, and even disable ordestroy critical infrastructure such as dams and power grids.

By first verifying the mobile device identity of the unlocking device,embodiments of the present invention are able to better protect bothpersonal and public IoT assets against the looming threat. In someembodiments, ownership of the device, for example, through the device'sown biometrics and the proximity to the IoT device may also be utilizedfor authentication.

Computing devices (e.g., mobile devices utilizing mobile apps, computersusing browsers, kiosks designed for a particular purpose) are widespreadand, coupled with single-sign-on systems for electronic account access(e.g., “logging in”), are used for everything from on-line banking,unlocking your home or car, accessing your social networkingenvironment, buying and selling tickets, etc. Most common, a usernameand password is required, but have been found to be very easy to crack,as many users are too forgetful or lazy to create secure passwords.Conventional two-factor authentication may help, but is full offriction—a user probably may have their username and password saved, butconventional two-factor authentication requires them to wait for a codeand then input the code before having access.

Embodiments of the present invention provide the safety of 2FA butrequire none of the friction of waiting for and subsequently enteringthe code. Other embodiments combine the process of frictionlesstwo-factor authentication with one or both a biometric input (e.g., afingerprint, retinal scan, or the like) and location data, toauthenticate both the device and one or both possession thereof orproximity thereto before, for example, unlocking your home or car orallowing access to your bank account.

BRIEF SUMMARY

Embodiments described herein provide frictionless two-factorauthentication. In particular, a method, apparatus, and computer programproduct are provided for receiving device identification informationfrom both a secured system indicating devices with authorization andfrom a network provider indicating the device attempting to access thesecured system to authenticate access.

In some embodiments, a method may be provided for performingfrictionless two-factor authentication, the method comprising receiving,from a first entity, an indication of a request received at the firstentity to access an account from a device associated with a user, theindication comprising at least one instance of first deviceidentification information of at least one device having authorizationto access the account, providing a network address to the first entity,the network address configured to be sent to the device from the firstentity, receiving, from a second entity, second device identificationinformation, the second device identification information determinedupon the device accessing to the network address, performing a real-timecomparison between the first device identification information andsecond device identification information, and prompting the first entityto grant the device access to the account if a match is detected betweenthe first device identification information and second deviceidentification information.

In some embodiments, the network address is a uniform resource locator(URL) address. In some embodiments, the first entity is a bank server.In some embodiments, the second entity is a cellular network provider ora cable network provider. In some embodiments, the method may furthercomprise determining a confidence level of (i) the first deviceidentification information and (ii) the second device identificationinformation match.

In some embodiments, the method may further comprise normalizing thefirst device identification information and the second deviceidentification information, and determining whether (i) the normalizedfirst device identification information and (ii) the normalized seconddevice identification information match.

In some embodiments, the first device identification information and thesecond device identification information is at least one of a telephonenumber, a device serial number, a unique serial number (ICCID), aninternational mobile subscriber identity (IMSI) number, or anInternational Mobile Equipment Identity (IMEI).

In some embodiments, the method may further comprise receiving a firstset of biometric data from the first entity, the first set of biometricdata used at log in at the first entity, receiving a second set ofbiometric data from the second entity, the second set of biometric dataused when accessing the network address, and performing a comparisonbetween the first set of biometric data and the second set of biometricdata.

In some embodiments, an apparatus may be provided for performingfrictionless two-factor authentication, the apparatus comprising atleast one processor and at least one memory including computer programcode, the at least one memory and the computer program code configuredto, with the processor, cause the apparatus to at least receive, from afirst entity, an indication of a request received at the first entity toaccess an account from a device associated with a user, the indicationcomprising at least one instance of first device identificationinformation of at least one device having authorization to access theaccount, provide a network address to the first entity, the networkaddress configured to be sent to the device from the first entity,receive, from a second entity, second device identification information,the second device identification information determined upon the deviceaccessing to the network address, perform a real-time comparison betweenthe first device identification information and second deviceidentification information, and prompt the first entity to grant thedevice access to the account if a match is detected between the firstdevice identification information and second device identificationinformation.

In some embodiments, the network address is a uniform resource locator(URL) address. In some embodiments, the first entity is a bank server.In some embodiments, the second entity is a cellular network provider ora cable network provider.

In some embodiments, the at least one memory and the computer programcode are further configured to, with the processor, cause the apparatusto determine a confidence level of (i) the first device identificationinformation and (ii) the second device identification information match.

In some embodiments, the at least one memory and the computer programcode are further configured to, with the processor, cause the apparatusto normalize the first device identification information and the seconddevice identification information, and determine whether (i) thenormalized first device identification information and (ii) thenormalized second device identification information match.

In some embodiments, the first device identification information and thesecond device identification information is at least one of a telephonenumber, a device serial number, a unique serial number (ICCID), aninternational mobile subscriber identity (IMSI) number, or anInternational Mobile Equipment Identity (IMEI).

In some embodiments, the at least one memory and the computer programcode are further configured to, with the processor, cause the apparatusto receive a first set of biometric data from the first entity, thefirst set of biometric data used at log in at the first entity, receivea second set of biometric data from the second entity, the second set ofbiometric data used when accessing the network address, and performing acomparison between the first set of biometric data and the second set ofbiometric data.

In some embodiments, a computer program product may be provided forperforming frictionless two-factor authentication, the computer programproduct comprising at least one non-transitory computer-readable storagemedium having computer-executable program code instructions storedtherein, the computer-executable program code instructions comprisingprogram code instructions for receiving, from a first entity, anindication of a request received at the first entity to access anaccount from a device associated with a user, the indication comprisingat least one instance of first device identification information of atleast one device having authorization to access the account, providing anetwork address to the first entity, the network address configured tobe sent to the device from the first entity, receiving, from a secondentity, second device identification information, the second deviceidentification information determined upon the device accessing to thenetwork address, performing a real-time comparison between the firstdevice identification information and second device identificationinformation, and prompting the first entity to grant the device accessto the account if a match is detected between the first deviceidentification information and second device identification information.

In some embodiments, the network address is a uniform resource locator(URL) address. In some embodiments, the first entity is a bank server.In some embodiments, the second entity is a cellular network provider ora cable network provider.

In some embodiments, the computer-executable program code instructionsfurther comprise program code instructions for determining a confidencelevel of (i) the first device identification information and (ii) thesecond device identification information match.

In some embodiments, the computer-executable program code instructionsfurther comprise program code instructions for normalizing the firstdevice identification information and the second device identificationinformation, and determining whether (i) the normalized first deviceidentification information and (ii) the normalized second deviceidentification information match.

In some embodiments, the first device identification information and thesecond device identification information is at least one of a telephonenumber, a device serial number, a unique serial number (ICCID), aninternational mobile subscriber identity (IMSI) number, or anInternational Mobile Equipment Identity (IMEI).

In some embodiments, the computer-executable program code instructionsfurther comprise program code instructions for receiving a first set ofbiometric data from the first entity, the first set of biometric dataused at log in at the first entity, receiving a second set of biometricdata from the second entity, the second set of biometric data used whenaccessing the network address, and performing a comparison between thefirst set of biometric data and the second set of biometric data.

In some embodiments, an apparatus may be provided for performingfrictionless two-factor authentication, the apparatus comprising meansfor receiving, from a first entity, an indication of a request receivedat the first entity to access an account from a device associated with auser, the indication comprising at least one instance of first deviceidentification information of at least one device having authorizationto access the account, means for providing a network address to thefirst entity, the network address configured to be sent to the devicefrom the first entity, means for receiving, from a second entity, seconddevice identification information, the second device identificationinformation determined upon the device accessing to the network address,means for performing a real-time comparison between the first deviceidentification information and second device identification information,and means for prompting the first entity to grant the device access tothe account if a match is detected between the first deviceidentification information and second device identification information.

In some embodiments, the network address is a uniform resource locator(URL) address. In some embodiments, the first entity is a bank server.In some embodiments, the second entity is a cellular network provider ora cable network provider.

In some embodiments, the apparatus may further comprise means fordetermining a confidence level of (i) the first device identificationinformation and (ii) the second device identification information match.

In some embodiments, the apparatus may further comprise means fornormalizing the first device identification information and the seconddevice identification information, and means for determining whether (i)the normalized first device identification information and (ii) thenormalized second device identification information match.

In some embodiments, the first device identification information and thesecond device identification information is at least one of a telephonenumber, a device serial number, a unique serial number (ICCID), aninternational mobile subscriber identity (IMSI) number, or anInternational Mobile Equipment Identity (IMEI).

In some embodiments, the apparatus may further comprise means forreceiving a first set of biometric data from the first entity, the firstset of biometric data used at log in at the first entity, means forreceiving a second set of biometric data from the second entity, thesecond set of biometric data used when accessing the network address,and means for performing a comparison between the first set of biometricdata and the second set of biometric data.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 is a block diagram of a system that may be specificallyconfigured in accordance with an example embodiment of the presentinvention;

FIG. 2 is a block diagram of an apparatus that may be specificallyconfigured in accordance with an example embodiment of the presentinvention;

FIGS. 3, 4A, and 4B are data flow diagrams, each showing an exemplaryoperation of an example system in accordance with an embodiment of thepresent invention; and

FIGS. 5, 6A, and 6B depict flowcharts, each showing an exemplary methodof operating an example apparatus in accordance with an embodiment ofthe present invention.

DETAILED DESCRIPTION

Some example embodiments will now be described more fully hereinafterwith reference to the accompanying drawings, in which some, but not allembodiments are shown. Indeed, the example embodiments may take manydifferent forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will satisfy applicable legal requirements. Likereference numerals refer to like elements throughout.

As used herein, the terms “data,” “content,” “information,” and similarterms may be used interchangeably to refer to data capable of beingtransmitted, received, and/or stored in accordance with embodiments ofthe present invention. Thus, use of any such terms should not be takento limit the spirit and scope of embodiments of the present invention.Further, where a computing device is described herein to receive datafrom another computing device, it will be appreciated that the data maybe received directly from the another computing device or may bereceived indirectly via one or more intermediary computing devices, suchas, for example, one or more servers, relays, routers, network accesspoints, base stations, hosts, and/or the like, sometimes referred toherein as a “network.” Similarly, where a computing device is describedherein to send data to another computing device, it will be appreciatedthat the data may be sent directly to the another computing device ormay be sent indirectly via one or more intermediary computing devices,such as, for example, one or more servers, relays, routers, networkaccess points, base stations, hosts, and/or the like.

Moreover, the term “exemplary”, as may be used herein, is not providedto convey any qualitative assessment, but instead merely to convey anillustration of an example.

Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present invention.

The term “device identification information” as used herein refers toany information that may identify a computing device. For example,device identification information may refer to a user's subscriberID,which may be similar or the same as a mobile device's phonenumber/CallerID number, the mobile device's phone number, the mobiledevice's callerID number, International Mobile Equipment Identity(IMEI)/unique serial number (ICCID)data, network-based, MAC addresses,billing record's modem certificate, DOCSIS hub/Media Access Layerrouting assignments, Cable modem's certificate, device serial number,etc., Intel vPro and Trusted Platform Module key, or the like. Deviceidentification information may be stored, transmitted, and/or received,in some embodiments, in a hashed, one-way hashed, encrypted, digitallysigned, using public/private key encryption or other means ofencrypting, or other similar algorithms (e.g., forsystem/customer/bank/wireless network/other privacy or other reasons)data form.

A “network provider” as used herein may be, for example, wirelessnetwork provider (e.g., Verizon, AT&T, T-Mobile, etc.) which may havedata such as a user's name, billing address, equipment installationaddress, birthdate, tower routing/router information to the user'swireless device (e.g., mobile phone), IP WAN address, IP LAN address, IPDMZ info, wireless device equipment information (serial number,certificate number, model number, IMEI number etc.), and otherinformation, that it could similarly supply to a third-party.

Similarly, a “network provider” may be, for example, in thoseembodiments in which a user may access the internet through a wiredconnection (e.g., via cable, DSL, any non-wireless-phone-carrier meanssuch as via a satellite dish system), a wired network provider. Forexample, a user's cable company (for example—cox cable) may have datasuch as a user's name, billing address, equipment installation address,birthdate, among other fields, cable wire routing/router information tothe user's cable modem (home), IP WAN address, IP LAN address, IP DMZinfo, cable modem equipment information (serial number, certificatenumber, model number, etc.), and other information, that it couldsimilarly supply to a third-party.

A “secured system” as used herein may refer to, for example, anyorganization, person, company, government, or other entity seeking toprovide a secure data environment, including, for example, a bank, ane-commerce company, an entertainment company, an IOT device/company,(IOT meaning internet of things), a fintech company, a social webcompany, a file storage company, or the like.

As used herein, a “match” may be detected, determined, and/or reportedin, for example, a binary form or a more granular form (e.g., a score,for example, ranging from 0-100 or the like).

System Architecture

Methods, apparatuses, and computer program products of the presentinvention may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a networked device, such as a server orother network entity, configured to communicate with one or moredevices, such as one or more user devices, network operators/providers,and providers of secured platforms, and payment systems (e.g., bankingsystems, payment systems, e-commerce platforms, IoT devices, IoT devicecompany or any other organization, person, company, government, or otherentity such as a fintech company, a social web platform or company, afile storage platform or company.). Additionally or alternatively, thenetworked device may include fixed computing devices, such as a personalcomputer or a computer workstation. Still further, example embodimentsmay be embodied by any of a variety of mobile terminals, such as aportable digital assistant (PDA), mobile telephone, smartphone, laptopcomputer, tablet computer, or any combination of the aforementioneddevices.

In this regard, FIG. 1 shows an example computing system within whichembodiments of the present invention may operate. In particular,authentication service 102, which may comprise server 114 and database116, may be operable to receive first device identification informationfrom secured system 104 indicative of, for example, a user or a devicehaving pre-authorized access to secured system 104, receive seconddevice identification information indicative of the actual user ordevice attempting to gain access to the secured system 104, compare thefirst and second device identification information, and in an instancein which they match, prompt the secured system 104 to allow access.Authentication service 102 may be embodied by, for example, a webserver, a cloud server, a Linux or LAMP server stack, a windows server,a mobile device, and be connected to the internet, wirelesscommunication infrastructure, and associated routers and other relateddevices

The server 114 may be embodied as a single computer or multiplecomputers and may provide for authenticating user and/or device accessto secured systems 104A-104N. Database 116 may be embodied as a datastorage device such as a Network Attached Storage (NAS) device ordevices, or as a separate database server or servers. Database 116includes information accessed and stored by the server 114 to facilitatethe operations of the authentication service 102.

Returning to FIG. 1, users operating, for example, user devices108A-108N may access or attempt to access secured systems 104A-104N viaa network 112 (e.g., the internet, or the like). In some embodiments,the data traffic may be routed through or otherwise be managed by thenetwork provider 110A-110N. The secured systems 104A-104N may access theauthentication service 102 via network 112 to, for example, authenticatethe user and/or device attempting to access the system. In an e-commerceembodiment, user devices 108A-108N and/or secured systems 104A-104N mayaccess or attempt to access, via a network 112, payment systems106A-106N.

The user devices 108A-108N may be any computing device as known in theart and operated by a user. Electronic data received by secured systems104A-104N, payment systems 106A-106N, or the network provider 110A-110Nfrom the user devices 108A-108N may be provided in various forms and viavarious methods. The user devices 108A-108N may include mobile devices,such as laptop computers, smartphones, netbooks, tablet computers,wearable devices (e.g., electronic watches, wrist bands, glasses, etc.),and the like. Such mobile devices may provide requests or search queriesto or otherwise attempt to access secured system 104.

In embodiments where a user device 108A-108N is a mobile device, such asa smart phone or tablet, the user device 108A-108N may execute an “app”or “user application” to interact with secured systems 104A-104N,payment systems 106A-106N and/or network provider 110A-110N. Such appsare typically designed to execute on mobile devices, such as tablets orsmartphones, without the use of a browser. For example, an app may beprovided that executes on mobile device operating systems such as AppleInc.'s iOS®, Alphabet Inc.'s Android®, or Microsoft Corp.'s Windows 10®.These platforms typically provide frameworks that allow apps tocommunicate with one another and with particular hardware and softwarecomponents of mobile devices. For example, the mobile operating systemsnamed above each provide frameworks for interacting with locationservices circuitry, wired and wireless network interfaces, usercontacts, and other applications in a manner that allows for improvedinteractions between apps while also preserving the privacy and securityof users. In some embodiments, a mobile operating system may alsoprovide for improved communication interfaces for interacting withexternal devices (e.g., home and/or or automobile security and/orautomation systems, navigation systems, and the like).

Communication with hardware and software modules executing outside ofthe app is typically provided via application programming interfaces(APIs) provided by the mobile device operating system.

Additionally or alternatively, user devices 108A-108N may interactthrough the secured systems 104A-104N and/or payment systems 106A-106Nvia a web browser. As yet another example, the user devices 108A-108Nmay include various hardware or firmware designed to interface with theone or more secured systems 104A-104N and/or payment systems 106A-106N(e.g., where the user devices 108A-108N is a purpose-built deviceoffered for the primary purpose of communicating with secured systems104A-104N and/or payment systems 106A-106N, such as a store kiosk).

Again, referring back to FIG. 1, System 100 supports communicationsbetween user devices 108A-108N and the secured systems 104A-104N and/orpayment systems 106A-106N, via network 112. While the system 100 maysupport communication via 5G, an Long Term Evolution (LTE) orLTE-Advanced (LTE-A) network, some embodiments may also supportcommunications between the user devices 108A-108N and the secured system104 including those configured in accordance with wideband code divisionmultiple access (W-CDMA), CDMA2000, global system for mobilecommunications (GSM), general packet radio service (GPRS), the IEEE802.11 standard including, for example, the IEEE 802.11ah or 802.11acstandard or other newer amendments of the standard, wireless localaccess network (WLAN), Worldwide Interoperability for Microwave Access(WiMAX) protocols, universal mobile telecommunications systems (UMTS)terrestrial radio access network (UTRAN) and/or the like, as well asother standards, for example, with respect to multi-domain networks,that may include, industrial wireless communication networks such asBluetooth, ZigBee etc. and/or the like.

Secured systems 104A-104N and/or payment systems 106A-106N may beembodied by any of a variety of network entities, such as, for example,a server or the like. In other embodiments, the network entities mayinclude mobile telephones, smart phones, portable digital assistants(PDAs), desktop computers, laptop computers, tablet computers any ofnumerous other hand held or portable communication devices, computationdevices, content generation devices, content consumption devices, (e.g.,mobile media player, a virtual reality device, a mixed reality device, awearable device, a virtual machine, a cloud-based device or combinationsthereof), Internet of Thing (IoT) devices, sensors, meters, or the like.

For example, the IoT devices, sensors, and/or meters may be deployed ina variety of different applications including in home and/or automobilesecurity and/or automation applications to serve, for example, inenvironmental monitoring applications, in industrial process automationapplications, vehicular or transportation automation application, inhealthcare and fitness applications, in building automation and controlapplications and/or in temperature sensing applications.

The authentication service 102 and/or server 114 may be embodied as orotherwise include an apparatus 200 that is specifically configured toperform the functions of the respective device, as genericallyrepresented by the block diagram of FIG. 2. While the apparatus may beemployed, for example, as shown in FIG. 2, it should be noted that thecomponents, devices or elements described below may not be mandatory andthus some may be omitted in certain embodiments. Additionally, someembodiments may include further or different components, devices orelements beyond those shown and described herein.

Apparatus Architecture

Regardless of the type of device that embodies the authenticationservice 102 or server 112, authentication service 102 or server 112 mayinclude or be associated with an apparatus 200 as shown in FIG. 2. Inthis regard, the apparatus may include or otherwise be in communicationwith a processor 202, a memory device 204, a communication interface206, a user interface 208, and comparison module 210. As such, in someembodiments, although devices or elements are shown as being incommunication with each other, hereinafter such devices or elementsshould be considered to be capable of being embodied within the samedevice or element and thus, devices or elements shown in communicationshould be understood to alternatively be portions of the same device orelement.

In some embodiments, the processor 202 (and/or co-processors or anyother processing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory device 204 via a busfor passing information among components of the apparatus. The memorydevice may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory devicemay be an electronic storage device (for example, a computer readablestorage medium) comprising gates configured to store data (for example,bits) that may be retrievable by a machine (for example, a computingdevice like the processor). The memory device may be configured to storeinformation, data, content, applications, instructions, or the like forenabling the apparatus 200 to carry out various functions in accordancewith an example embodiment of the present invention. For example, thememory device could be configured to buffer input data for processing bythe processor. Additionally or alternatively, the memory device could beconfigured to store instructions for execution by the processor.

As noted above, the apparatus 200 may be embodied by authenticationservice 102 or server 114 configured to employ one or more exampleembodiments of the present invention. However, in some embodiments, theapparatus may be embodied as a chip or chip set. In other words, theapparatus may comprise one or more physical packages (for example,chips) including materials, components and/or wires on a structuralassembly (for example, a baseboard). The structural assembly may providephysical strength, conservation of size, and/or limitation of electricalinteraction for component circuitry included thereon. The apparatus maytherefore, in some cases, be configured to implement an embodiment ofthe present invention on a single chip or as a single “system on achip.” As such, in some cases, a chip or chipset may constitute meansfor performing one or more operations for providing the functionalitiesdescribed herein.

The processor 202 may be embodied in a number of different ways. Forexample, the processor may be embodied as one or more of varioushardware processing means such as a coprocessor, a microprocessor, acontroller, a digital signal processor (DSP), a processing element withor without an accompanying DSP, or various other processing circuitryincluding integrated circuits such as, for example, an ASIC (applicationspecific integrated circuit), an FPGA (field programmable gate array), amicrocontroller unit (MCU), a hardware accelerator, a special-purposecomputer chip, or the like. As such, in some embodiments, the processormay include one or more processing cores configured to performindependently. A multi-core processor may enable multiprocessing withina single physical package. Additionally or alternatively, the processormay include one or more processors configured in tandem via the bus toenable independent execution of instructions, pipelining and/ormultithreading.

In an example embodiment, the processor 202 may be configured to executeinstructions stored in the memory device 204 or otherwise accessible tothe processor. Alternatively or additionally, the processor may beconfigured to execute hard coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor may represent an entity (for example, physically embodiedin circuitry) capable of performing operations according to anembodiment of the present invention while configured accordingly. Thus,for example, when the processor is embodied as an ASIC, FPGA or thelike, the processor may be specifically configured hardware forconducting the operations described herein. Alternatively, as anotherexample, when the processor is embodied as an executor of softwareinstructions, the instructions may specifically configure the processorto perform the algorithms and/or operations described herein when theinstructions are executed. However, in some cases, the processor may bea processor of a specific device configured to employ an embodiment ofthe present invention by further configuration of the processor byinstructions for performing the algorithms and/or operations describedherein. The processor may include, among other things, a clock, anarithmetic logic unit (ALU) and logic gates configured to supportoperation of the processor. In one embodiment, the processor may alsoinclude user interface circuitry configured to control at least somefunctions of one or more elements of the user interface 208.

Meanwhile, the communication interface 206 may be any means such as adevice or circuitry embodied in either hardware or a combination ofhardware and software that is configured to receive and/or transmitdata. In this regard, the communication interface 206 may include, forexample, an antenna (or multiple antennas) and supporting hardwareand/or software for enabling communications wirelessly. Additionally oralternatively, the communication interface may include the circuitry forinteracting with the antenna(s) to cause transmission of signals via theantenna(s) or to handle receipt of signals received via the antenna(s).For example, the communications interface may be configured tocommunicate wirelessly with wearable device (e.g., head mounteddisplays), such as via Wi-Fi, Bluetooth or other wireless communicationstechniques. In some instances, the communication interface mayalternatively or also support wired communication. As such, for example,the communication interface may include a communication modem and/orother hardware/software for supporting communication via cable, digitalsubscriber line (DSL), universal serial bus (USB) or other mechanisms.For example, the communication interface may be configured tocommunicate via wired communication with other components of thecomputing device.

The user interface 208 may be in communication with the processor 202,such as the user interface circuitry, to receive an indication of a userinput and/or to provide an audible, visual, mechanical, or other outputto a user. As such, the user interface may include, for example, akeyboard, a mouse, a joystick, a display, a touch screen display, amicrophone, a speaker, and/or other input/output mechanisms. In someembodiments, a display may refer to display on a screen, on a wall, onglasses (for example, near-eye-display), in the air, etc. The userinterface may also be in communication with the memory 204 and/or thecommunication interface 206, such as via a bus.

Data Flow

FIG. 3 depicts an example data flow 300 illustrating interactionsbetween a user device, for example, a user device 302 such as one ofuser devices 108A-108N, a secured system 304 such as one of Securedsystems 104A-104N, a network provider 306 such as one of networkproviders 110A-110N and authentication system 102. The data flow 300illustrates how electronic information may be passed among varioussystems in accordance with embodiments of the present invention.

At step 302, user device 350 transmits data (e.g., a page request) or,for example in some embodiments, launches an API, attempting to accesssecured system 360. At 304, a login page is provided and a user,operating user device 306, provides login credentials. In someembodiments, login credentials are saved and the providing of the logincredentials requires no instant input from the user.

The secured system, requiring two-factor authentication, then at step308 requests authentication of the user device by providing anauthentication request and, for example first device identificationinformation to the authentication service 380. The first deviceidentification information may comprise one or more phone numbers foreach of one or more user devices having pre-authorized access to thesecured system. For example, when registering or at a previous login, auser may provide a list of authorized devices and/or deviceidentification information of authorized devices, giving them access tothe account.

The system, in an effort to determine the identification information ofthe user device that is currently attempting access to the securedsystem may perform one or more of a number of processes. Generally, thesystem may be configured to direct the user device to a destinationwhere the identification information may be determined, detected,identified, or otherwise accessed. For example, the user device may beprovided with a URL to ping, an app to which to connect, or the like.The destination may be received from, in some embodiments, the securedsystem, while in other embodiments, the destination may be received fromauthentication service. The destination may be provided directly to theuser device, to a browser executing thereon, to an app executing there,via an API call, via a bot, by sending an SMS message thereby requiringa click, via a notification from an app, or any other form of, forexample, user-to-machine electronic communication.

The authentication service 380 may, for example, at step 310 request anetwork address and at step 312 receive the network address, the networkaddress, for example, may be a URL or the like configured to be passedto the secured system or directly to the user device, for the userdevice to ping or otherwise access. As such, at step 314, theauthentication service provides the network address to the securedsystem and at step 316, the network address is provided to the userdevice. At step 318, the user device pings or otherwise access thenetwork address, where, for example, the network provider, at step 320,receives, reads, extracts, or otherwise determines the deviceidentification information, for example, from a packet header.

In particular, a user device may store or otherwise be associated withidentification information. For example, in a mobile context, asubscriber identification module (SIM), Universal Subscriber IdentityModule (USIM), a Removable User Identity Module (R-UIM), or a CDMASubscriber Identity Module (CSIM), any of which may be a softwareapplication or integrated circuit, for example, stored on a SIM card orUniversal Integrated Circuit Card (UICC), may comprise at least a uniqueserial number (ICCID) or an international mobile subscriber identity(IMSI) number. The SIM card, as referred to herein, may be a mini,micro, nano, virtual, or emdedded(e) SIM.

At step 322, the network provider provides and the authenticationservice receives the second device identification information, whichindicates the device identification information of the device attemptingto access secured system 360. In an instance in which no deviceidentification of the device attempting to access secured system 360(e.g., second device identification information) is available or able tobe determined, detected, identified, or otherwise accessed, theauthentication service may be configured to perform a different processfor two-factor authentication where, for example, the authenticationservice, utilizing the first identification information provides a codeor the like to the user device, and the request the user to provide, viathe user device, the code (e.g., input into the app or browser) to thesecured system, for example, which may have the authentication sessionopen.

At step 324, the authentication service compares the first deviceidentification information and the second device identificationinformation. In some embodiments, as one of ordinary skill in the artwould understand, the first device identification information asreceived from the secured system and/or the second device identificationinformation as received from the network provider may be raw, tokenized,hashed, or otherwise transcoded, for example, for security reasons. Thecomparison may first involve, for example, decoding the deviceidentification information and comparing raw data or comparingtranscoded information. The comparison may also involve, in someembodiments, normalization of the device identification information.That is, the first identification information may be in a convenientformat, for example, for input or display within the user's onlineaccount—which may or may not include elements such as punctuation (e.g.,dashes, parentheses, brackets, or the like), country codes, spaces, etc.the comparison may simply ignore such elements, strip the elements, orotherwise clean the data, etc.

In some embodiments, because page requests are monitored, directed, orotherwise pass through network provider 370, the second deviceidentification information may be passed to the secured system at theinitial request—enabling the secured system to pass data, for example,the data packet header, which may be tokenized, hashed, or otherwisetranscoded, to the authentication system with or after the first deviceidentification information.

Upon making the comparison, the authentication service 380, at step 326,in an instance in which the comparison determines that a match existsbetween for example, the first device identification information and thesecond device identification information, may authenticate and/or promptthe secured system to authenticate or grant access to the user device.The secured system may then, at step 328, grant access to the userdevice.

However, in an instance in which the comparison determines that no matchexists between for example, the first device identification informationand the second device identification information, the authenticationservice 380, at step 330, may notify and/or prompt the secured systemindicating its inability to authenticate. The secured system may then,at step 332, deny access to the user device.

FIG. 4A depicts an example data flow 400 illustrating interactionsbetween a user device, for example, a user device 302 such as one ofuser devices 108A-108N, a secured system 304 such as one of securedsystems 104A-104N, a network provider 306 such as one of networkproviders 110A-110N and authentication system 102. The data flow 300illustrates how electronic information may be passed among varioussystems in accordance with embodiments of the present invention, and inparticular, FIG. 4 shows how the use of biometric data may augment orotherwise aid in the authentication process of FIG. 3.

In some embodiments, upon a determination that the first deviceidentification information matches the second device identificationinformation, the secured system and/or the authentication service may beconfigured to perform additional authentication. While in otherembodiments, the secured system and/or the authentication service may beconfigured to perform authentication using both the frictionlesstwo-factor authentication shown in FIG. 3 as well as biometric data.That is, in an instance in which both the frictionless two-factorauthentication shown in FIG. 3 as well as biometric data are used inparallel, the secured system may be configured to provide, at step 308,for example, biometric data of one or more users having been previouslyauthorized to access the system. In other embodiments, for example, asshown in FIG. 4A, biometric data may be provided upon the determinationthat the first device identification information matches the seconddevice identification information.

Regardless of when the biometric data of one or more users having beenpreviously authorized to access the system is received, as shown at step410, the authentication service may request the biometric data of theuser operating the device currently attempting to access the securedsystem, and at step 415, that biometric data is received. Subsequently,at step 420, the authentication service may be configured to determinewhether the previously registered biometric data and current biometricdata match.

Similar to FIG. 3, in an instance in which the comparison determinesthat a match exists between for example, the previously registeredbiometric data and current biometric data, the authentication service,at step 425, may authenticate and/or prompt the secured system toauthenticate or grant access to the user device. The secured system maythen, at step 430, grant access to the user device.

However, in an instance in which the comparison determines that no matchexists, the authentication service 380 may notify and/or prompt thesecured system that the match as not made. The secured system may thendeny access to the secured system.

FIG. 4B depicts an example data flow 400 illustrating interactionsbetween a user device, for example, a user device 302 such as one ofuser devices 108A-108N, a secured system 304 such as one of securedsystems 104A-104N, a network provider 306 such as one of networkproviders 110A-110N and authentication system 102. The data flow 300illustrates how electronic information may be passed among varioussystems in accordance with embodiments of the present invention, and inparticular, FIG. 4 shows how the use of location data may augment orotherwise aid in the authentication process of FIG. 3.

In some embodiments, upon a determination that the first deviceidentification information and the second device identificationinformation match, the secured system and/or the authentication servicemay be configured to perform additional authentication. In otherembodiments, the secured system and/or the authentication service may beconfigured to perform authentication using both the frictionlesstwo-factor authentication shown in FIG. 3 as well as location data.

In an instance in which both the frictionless two-factor authenticationshown in FIG. 3 as well as location data are used in parallel, thesecured system may be configured to provide, at step 308 for example,location data of one or more users having been previously authorized toaccess the system. In other embodiments, for example, as shown in FIG.4B, location data may be provided upon the determination that the firstdevice identification information matches the second deviceidentification information.

Furthermore, in an instance in which both the frictionless two-factorauthentication shown in FIG. 3 as well as location data are used inparallel, the network provider may be configured to provide, forexample, at step 322, location data of the user device currentlyattempting to access the secured system. Similar to the deviceidentification information, the user device, for example, within a datapacket header or the like, may provide location information to thenetwork provider, while in other embodiments, the network provider maydetermine the location, within a particular variance, based on where theconnection is made. In other embodiments, for example, as shown in FIG.4B, location data may be provided upon the determination that the firstdevice identification information matches the second deviceidentification information.

If however, the location data of one or more users having beenpreviously authorized to access the system has not been receivedpreviously, as shown at step 455, the authentication service may requestand receive the location data of one or more users having beenpreviously authorized to access the secured system.

In an instance in which the location data of the user device currentlyattempting to access the secured system has not been receivedpreviously, as shown at step 460, the authentication service may requestand, at step 465, receive, from the network provider, the location dataof the user device currently attempting to access the secured system. Inanother embodiment, which may also be performed, as shown at step 470,the authentication service may request from the user device, and, atstep 475, receive, from the user device, the location data of the userdevice currently attempting to access the secured system. Subsequently,at step 480, the authentication service may be configured to determinewhether the previously registered location data and current locationdata match.

Similar to FIG. 3, in an instance in which the comparison determinesthat a match exists between for example, the previously registeredlocation data and current location data, the authentication service, atstep 485, may authenticate and/or prompt the secured system toauthenticate or grant access to the user device. The secured system maythen, at step 490, grant access to the user device. However, in aninstance in which the comparison determines that no match exists, theauthentication service 380 may notify and/or prompt the secured systemthat the match as not made. The secured system may then deny access tothe secured system.

Exemplary Operation for Implementing Embodiments of the PresentInvention

In some embodiments, apparatus 200 may be configured to performfrictionless two-factor authentication. FIGS. 5, 6A, and 6B illustrateexemplary processes for determining whether to authenticate a userdevice, prompting the approval or denial of access to an account.

Receiving an Authentication Request

FIG. 5 illustrates a flow diagram depicting an example of a process 500for authenticating a device in accordance with embodiments of thepresent invention. The process illustrates how, upon reception of theauthentication request, an authentication system or an API relatedthereto may receive identification information of devices havingpreviously given authorization to access a secured system (e.g., abanking account) and identification information of a device currentlyattempting to access the secured system, and upon reception, performinga real-time match to determine whether to prompt the secured system toallow access. The process 500 may be performed by an apparatus, such asthe apparatus 200 described above with respect to FIG. 2.

A first entity (e.g., a secured system as described above, which mayinclude, for example, an online banking platform) may receive the logincredentials to an account. Upon receiving the login credentials, thefirst entity opens an authentication session, for example, via an APIprovided by the authentication service. As such, as shown in block 505of FIG. 5, an apparatus, for example, apparatus 200 embodied by, forexample, authentication service 102, server 114, or the like, may beconfigured to receive, from a first entity, an indication of a request.In some embodiments, the request is or was received at the first entity,to access an account from a device associated with a user. Theindication of the request, as received at the authentication service maycomprise at least one instance of first device identificationinformation of at least one user and/or device having authorization toaccess the account.

For example, at registration or any time thereafter, a user may providetheir bank or online banking platform with a list of one or more phonenumbers (e.g., their cellular phone number). In other embodiments, auser may provide a list of users (e.g., their first and last names orthe like) authorized to access an account. As such, upon receiving arequest to access the account, the first entity may provide one or moreinstances of device identification information in their possessionindicative of users or devices having authorized access.

The authentication service, upon receiving the indication of the requestto access the secured system, may initiate a process in which itdetermines the device identification information of the device currentlyattempting to access the account. In some embodiments, theauthentication service may provide the first entity or the device,directly, with a URL to ping. As shown in block 510 of FIG. 5, anapparatus, for example, apparatus 200 embodied by, for example,authentication service 102, server 114, or the like, may be configuredto transmit, to a second entity, a request for a network address and asshown in block 515 of FIG. 5, the apparatus, for example, apparatus 200embodied by, for example, authentication service 102, server 114, or thelike, may be configured to receive, from the second entity, the networkaddress.

Once in possession of network address, the authentication service maythen, as described above, transmit the network address to the firstentity or directly to the device. As such, as shown in block 520 of FIG.5, an apparatus, for example, apparatus 200 embodied by, for example,authentication service 102, server 114, or the like, may be configuredto provide the network address to the first entity. The network addressmay be configured to be sent to the device from the first entity.

Subsequent to the device pinging or otherwise attempting to access thenetwork address, the network provider may detect, determine or otherwiseidentify, for example, device identification information of the devicecurrently attempting to access the account and then transmit the deviceidentification information to the authentication service. Theauthentication then receives that information, in particular, forexample, a subscriberID (e.g., a phone number) and/or, in someembodiments, other information, as described above, that the networkprovider may have associated with the device (e g, name on account,billing address, or the like). Accordingly, as shown in block 525 ofFIG. 5, an apparatus, for example, apparatus 200 embodied by, forexample, authentication service 102, server 114, or the like, may beconfigured to receive, from a second entity, second deviceidentification information. In some embodiments, the second deviceidentification information may be determined upon the device pinging orotherwise accessing or attempting to the network address.

As one of ordinary skill would appreciate, the format of the informationmay vary. For example, the first identification information maycomprise, as described above, punctuation, spaces, etc. whereas thesecond device identification information may be in a same or differentformat. Therefore, in some embodiments, the authentication may “clean”or normalize the device identification information, for example, to aidin the comparison of the first identification information to the secondidentification information. As such, as shown in block 530 of FIG. 5, anapparatus, for example, apparatus 200 embodied by, for example,authentication service 102, server 114, or the like, may be configuredto normalize the data.

Having both the first identification information and the secondidentification information, a comparison may be made. Accordingly, asshown in block 535 of FIG. 5, an apparatus, for example, apparatus 200embodied by, for example, authentication service 102, server 114, or thelike, may be configured to perform a real-time comparison between thefirst device identification information and second device identificationinformation.

In an instance of a match between the first device identificationinformation and second device identification information, as shown inblock 540 of FIG. 5, an apparatus, for example, apparatus 200 embodiedby, for example, authentication service 102, server 114, or the like,may be configured to prompt the first entity to grant the device accessto the account. That is, where a match is detected, the authenticationservice may determine that device attempting to access the account is,in fact, authorized to access the account, and may notify the securedsystem.

In an instance of no match between the first device identificationinformation and second device identification information, as shown inblock 545 of FIG. 5, an apparatus, for example, apparatus 200 embodiedby, for example, authentication service 102, server 114, or the like,may be configured to prompt the first entity to deny the device accessto the account. That is, where a match is not detected, theauthentication service may not determine that device attempting toaccess the account is, in fact, authorized to access the account, andmay notify the secured system inasmuch.

In some embodiments, the authentication service may report a binaryresult (e.g., match/no match). As described above, in some embodiments,however, the authentication service may report more granular results,such as, for example, a confidence level. For example, where the phonenumber of a device attempting to access the account does not match apre-authorized phone number, the authentication service may see thatidentification information (e.g., a name on the account) matches a nameto which the phone number of the device attempting the account isregistered. As such, a binary result may be that of no match, a moregranular result may provide the secured system with confidence to allowaccess or, in some embodiments, prompt for more information. In someembodiments, the first device identification information may compriseeach of a plurality of data elements such as, for example, a phonenumber, a name, and a location (GPS related, a billing address, or thelike). The second device identification information, for example,received from the network provider after the device pings the providednetwork address, may provide a subset of the data elements included inthe first device identification information. The authentication servicemay calculate a non-binary result upon making the comparison of thefirst device identification information and the second deviceidentification information.

FIGS. 6A and 6B illustrate flow diagrams depicting example processes 600and 650, respectively, for authenticating a device and a user inaccordance with embodiments of the present invention. The processesillustrates how, upon reception of the authentication request, anauthentication service or an API related thereto may first, perform thetwo-factor authentication process as shown in FIG. 5, and uponauthentication of the device, authenticate the user of the device usingbiometric data and location data, respectively. As one of ordinary skillwould appreciate from the following disclosure, an authenticationservice or an API related thereto may first, perform the two-factorauthentication process as shown in FIG. 5, and upon authentication ofthe device, further perform authentication of the device using locationdata and/or the user of the device using biometric data. That is, africtionless three-factor authentication process is disclosed which mayinclude either the frictionless two-factor authentication process ofFIG. 5 and either of the processes shown in FIG. 6A or 6B. And africtionless four-factor authentication process is disclosed which mayinclude the frictionless two-factor authentication process of FIG. 5 andthe processes shown in FIG. 6A or 6B, each of which may be performed inparallel or in any order.

FIG. 6A illustrates a flow diagram depicting an example of a process 600for authenticating a device and a user in accordance with embodiments ofthe present invention. The process illustrates how, upon reception ofthe authentication request, an authentication service or an API relatedthereto may first, perform the two-factor authentication process asshown in FIG. 5, and upon authentication of the device, authenticate theuser of the device using biometric data. The process 600 may beperformed by an apparatus, such as the apparatus 200 described abovewith respect to FIG. 2.

The process of FIG. 6A may include those steps of FIG. 5, for example,as shown in blocks 505-530, related to receiving. As shown in block 605of FIG. 6A, an apparatus, for example, apparatus 200 embodied by, forexample, authentication service 102, server 114, or the like, may beconfigured to. Subsequently, as shown in block 535 of FIG. 5, anapparatus, for example, apparatus 200 embodied by, for example,authentication service 102, server 114, or the like, may be configuredto perform a real-time comparison between the first deviceidentification information and second device identification information.

In an instance of a match between the first device identificationinformation and second device identification information, as shown inblock 605 of FIG. 6, an apparatus, for example, apparatus 200 embodiedby, for example, authentication service 102, server 114, or the like,may be configured to prompt or request the first entity for biometricdata.

As shown in block 610 of FIG. 6A, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to receive, from a first entity, with theindication of a request, received at the first entity, to access anaccount from a device associated with a user, first biometric data, thefirst biometric data captured at the device.

As shown in block 615 of FIG. 6A, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to receive second biometric data, the secondbiometric data being data associated with users having been grantedauthorized access to the account. For example, a user may haveregistered his fingerprint at account set up or any previous time ofaccess.

As shown in block 620 of FIG. 6A, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to normalize the biometric data.

As shown in block 625 of FIG. 6A, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to perform a real-time comparison betweenthe first biometric data and the second biometric data.

In an instance of a match between the first biometric data and secondbiometric data, as shown in block 630 of FIG. 6A, an apparatus, forexample, apparatus 200 embodied by, for example, authentication service102, server 114, or the like, may be configured to prompt the firstentity to grant the device access to the account.

In an instance of no match between the first biometric data and secondbiometric data, as shown in block 635 of FIG. 6A, an apparatus, forexample, apparatus 200 embodied by, for example, authentication service102, server 114, or the like, may be configured to prompt the firstentity to deny the device access to the account.

FIG. 6B illustrates a flow diagram depicting an example of a process 650for authenticating a device and a user in accordance with embodiments ofthe present invention. The process illustrates how, upon reception ofthe authentication request, an authentication service or an API relatedthereto may first, perform the two-factor authentication process asshown in FIG. 5, and upon authentication of the device, authenticate theuser of the device using location data. The process 600 may be performedby an apparatus, such as the apparatus 200 described above with respectto FIG. 2.

The process of FIG. 6B may include those steps of FIG. 5, for example,as shown in blocks 505-530, related to receiving the first deviceidentification information and second device identification information.Subsequently, as shown in block 535 of FIG. 5, an apparatus, forexample, apparatus 200 embodied by, for example, authentication service102, server 114, or the like, may be configured to perform a real-timecomparison between the first device identification information andsecond device identification information.

In an instance of a match between the first device identificationinformation and second device identification information, as shown inblock 655 of FIG. 6B, an apparatus, for example, apparatus 200 embodiedby, for example, authentication service 102, server 114, or the like,may be configured to prompt or request the first entity for locationdata.

In some embodiments, the process of FIG. 6B may include those steps ofFIG. 6A, for example, as shown in blocks 605-635, related to receivingthe first biometric data and second biometric data. In thoseembodiments, and in an instance of a match between the first biometricdata and second biometric data, as shown in block 655 of FIG. 6B, anapparatus, for example, apparatus 200 embodied by, for example,authentication service 102, server 114, or the like, may be configuredto prompt or request the first entity for location data.

Regardless of whether the apparatus is using the frictionless two-factorauthentication process as shown in FIG. 5 or supplementing the processof FIG. 5 as shown in FIG. 6A, the apparatus may be configured forfurther authenticating access using location. As shown in block 660 ofFIG. 6B, an apparatus, for example, apparatus 200 embodied by, forexample, authentication service 102, server 114, or the like, may beconfigured to receive, from a first entity, with the indication of arequest, received at the first entity, to access an account from adevice associated with a user, first location data. The first locationdata may be captured at the device and/or, in some embodiments, capturedfrom the network provider (e.g., via triangulation, connections to acellular base station having a known location and a radius, connectionto a Wi-Fi access point, connection via Bluetooth, ZigBee or the like).

As shown in block 665 of FIG. 6B, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to receive second location data, the secondlocation data being data associated with users having been grantedauthorized access to the account. For example, a user may haveregistered his address (e.g., home address, work address, or the like)at account set up or any previous time of access.

As shown in block 670 of FIG. 6B, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to normalize the location data.

As shown in block 675 of FIG. 6B, an apparatus, for example, apparatus200 embodied by, for example, authentication service 102, server 114, orthe like, may be configured to perform a real-time comparison betweenthe first location data and the second location data.

In an instance of a match between the first location data and secondlocation data, as shown in block 680 of FIG. 6B, an apparatus, forexample, apparatus 200 embodied by, for example, authentication service102, server 114, or the like, may be configured to prompt the firstentity to grant the device access to the account.

In an instance of no match between the first location data and secondlocation data, as shown in block 685 of FIG. 6B, an apparatus, forexample, apparatus 200 embodied by, for example, authentication service102, server 114, or the like, may be configured to prompt the firstentity to deny the device access to the account.

Use Cases

In an example embodiment of the present invention, an apparatus orcomputer program product may be provided to implement or execute amethod, process, or algorithm for facilitating frictionless two-factorauthentication in the attempted access to an IoT device such as, forexample, (i) a security system (e.g., a physical lock outfitted with anembodiment of the present invention) protecting or otherwise controllingaccess to a home, apartment, a hotel room, an automobile, storage unit,safe, lock (e.g., bike lock, case lock, briefcase lock, luggage lock, orthe like), etc., (ii) an automation system (e.g., a system configuredfor controlling an automobile, one or more various switches in a poweror dam system), or (iii) a ticketing system.

Here, the user, for example, operating a user device with a mobile appinstalled thereon with a particular purpose (e.g., accessing securitysystem such as the lock on their car) opens the app, which may or maynot require login credentials. Once logged in, the user may then send acommand to the security or automation system. The command serves as therequest to access. As such, as described with regard to FIG. 5, theauthentication service receives the indication of the request.

Two different embodiments exist. First, where the user device and thesecurity system have access to, for example, a wireless network (e.g., acellular network, a Wi-Fi network, a private network, or the like) theprocess may continue as above. In particular, the user device sends thecommand to, for example, the secured system (e.g., an IoT deviceconfigured for unlocking your), the authentication service receives theindication of the request, the user device pings a network address, andthe authentication service is provided with device identificationinformation indicating the user device currently attempting to accessthe security system. In the case of a match, the lock opens by, in oneinstance where the security system is remote, the security systemsending a signal to the lock instructing it to open, or in an instancein which the security system is local, instructing the lock to open.Moreover, as described above, the authentication service may beconfigured to further authenticate by confirming the ownership of thedevice via biometric data and/or proximity via location data.

In another embodiment, a user device, which may typically have access toa cellular network or wireless cable network, does not, temporarily orpermanently, have access to the cellular network or the wireless cablenetwork. In such case, a local proximity network may be used using, forexample, local proximity network signals. For example, uponestablishing, for example, a Bluetooth connection with the user device,the security system may receive the command (e.g., a request to access),which when using local proximity network signals (e.g., Bluetooth,Near-field radio signals, RF signals, etc.) does provide deviceidentification information (i.e. a Bluetooth connection is onlyestablished by the requesting device identifying itself) and initiate anauthentication session with the authentication service, for example,locally. The security system, in providing the indication of therequest, provides both the device identification information provided bythe device attempting access provided in establishing the Bluetoothconnection and locally stored device identification information. Theauthentication service then compares the first device identificationinformation and second device identification information as describedabove, and prompts the security system as described above. As such, evenwith no “outside” connection, the frictionless two-factor authenticationsystem described herein may operate.

In the instance of a ticketing system, upon sale or re-sale of a ticket,embodiments of the present invention may be used to confirm authenticityof the ticket and owner combination. For example, a ticketing system mayenable resale of a ticket (e.g., a season ticket hold is unable to makea game and sells the ticket). Before the sale is confirmed, a userhaving offered the ticket for sale, received, and accepted an offer, maysend a command to the ticketing system, for example, configured toenable their collection of the payment and transfer of the ticket. Theticketing system may open an authentication session with theauthentication service and provide the authentications service with theuser device information of the user device known to having lastpurchased the ticket (e.g., the first device identificationinformation). The user device pings to network address, and the networkprovider provides, to the authentication service, the deviceidentification information of the device currently attempting to accessthe ticketing system (e.g., the second device identificationinformation). Upon a match, the authentication service may prompt theticketing system to complete the transaction—whereas, in an instance inwhich there is no match (the device identification information of thedevice attempting to sell a ticket does not match the deviceidentification information of the device having last purchased theticket), the authentication service prompts the ticketing system to denythe transaction.

Moreover, when attempting to access an event, a user device may presenta ticket to a ticket collection device/kiosk connected to the ticketingsystem, the presentment of the ticket being the request to access. Theticketing system (or the ticket collection device/kiosk) may initiate anauthentication session with the authentication service. Again, theauthentication service is provided with the indication of the requestthe device identification information of the user device having lastpurchased the ticket (e.g., the first device identificationinformation). The ticketing system may then prompt the user device toping a network address, the user device pings to network address, andthe network provider provides, to the authentication service, the deviceidentification information of the device currently attempting to accessthe ticketing system (e.g., the second device identificationinformation). After comparison, upon a match, the authentication servicemay prompt the ticketing system to allow entry—whereas, in an instancein which there is no match (the device identification information of thedevice attempting to utilize the ticket for entrance does not match thedevice identification information of the device having last purchasedthe ticket), the authentication service prompts the ticketing system todeny entry.

In another use case, for instance, in the initial establishment of anaccount, where a user only provides registration information, and, forexample, the secured system does not provide first device identificationinformation (e.g., there is no previously authorized device), theauthentication service may be configured to determine, detect, identify,or otherwise access one or more databases with information able tocorrelate that information the secured system does provide (e.g., theregistration information, such as name and address) with the seconddevice identification information.

In particular, a user operating a user device initiates a process toopen an account. Some amount of registration information is necessary.The secured system may then initiate an authentication session with theauthentication service and, provide the registration information, withthe indication of the request. The user device pings the network addressand the authentication service receives the second device identificationinformation.

Operation

FIGS. 3, 4A, 4B, 5, 6A, and 6B show data flows or flowcharts(hereinafter, flowcharts) of the exemplary operations performed by amethod, apparatus and computer program product in accordance withembodiments of the present invention. It will be understood that eachblock of the flowcharts, and combinations of blocks in the flowcharts,may be implemented by various means, such as hardware, firmware,processor, circuitry and/or other device associated with execution ofsoftware including one or more computer program instructions. Forexample, one or more of the procedures described above may be embodiedby computer program instructions. In this regard, the computer programinstructions which embody the procedures described above may be storedby a memory 206 of an apparatus employing an embodiment of the presentinvention and executed by a processor 204 in the apparatus. As will beappreciated, any such computer program instructions may be loaded onto acomputer or other programmable apparatus (for example, hardware) toproduce a machine, such that the resulting computer or otherprogrammable apparatus provides for implementation of the functionsspecified in the flowchart block(s). These computer program instructionsmay also be stored in a non-transitory computer-readable storage memorythat may direct a computer or other programmable apparatus to functionin a particular manner, such that the instructions stored in thecomputer-readable storage memory produce an article of manufacture, theexecution of which implements the function specified in the flowchartblock(s). The computer program instructions may also be loaded onto acomputer or other programmable apparatus to cause a series of operationsto be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructions whichexecute on the computer or other programmable apparatus provideoperations for implementing the functions specified in the flowchartblock(s). As such, the operations of FIGS. 3, 4A, 4B, 5, 6A, and 6B whenexecuted, convert a computer or processing circuitry into a particularmachine configured to perform an example embodiment of the presentinvention. Accordingly, the operations of FIGS. 3, 4A, 4B, 5, 6A, and 6Bdefine an algorithm for configuring a computer or processing to performan example embodiment. In some cases, a general purpose computer may beprovided with an instance of the processor which performs the algorithmsof FIGS. 3, 4A, 4B, 5, 6A, and 6B to transform the general purposecomputer into a particular machine configured to perform an exampleembodiment.

Accordingly, blocks of the flowchart support combinations of means forperforming the specified functions and combinations of operations forperforming the specified functions. It will also be understood that oneor more blocks of the flowcharts, and combinations of blocks in theflowcharts, can be implemented by special purpose hardware-basedcomputer systems which perform the specified functions, or combinationsof special purpose hardware and computer instructions.

In some embodiments, certain ones of the operations herein may beunnecessary, modified or further amplified. It should be appreciatedthat each of the modifications, optional operations or amplificationsmay be included with the operations either alone or in combination withany others among the features described herein.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

What is claimed is:
 1. A method for performing frictionless two-factorauthentication, the method comprising: receiving, from a first entity,an indication of a request received at the first entity to access anaccount from a device associated with a user, the indication comprisingat least one instance of first device identification information of atleast one device having authorization to access the account; providing anetwork address to the first entity, the network address configured tobe sent to the device from the first entity; receiving, from a secondentity, second device identification information, the second deviceidentification information determined upon the device accessing to thenetwork address; normalizing the first device identification informationand the second device identification information; performing a real-timecomparison between the first device identification information andsecond device identification information, wherein the real-timecomparison between the first device identification information andsecond device identification information comprises determining whether(i) the normalized first device identification information and (ii) thenormalized second device identification information match; and promptingthe first entity to grant the device access to the account if a match isdetected between the normalized first device identification informationand the normalized second device identification information.
 2. Themethod according to claim 1, wherein the network address is a uniformresource locator (URL) address.
 3. The method according to claim 1,wherein the first entity is a bank server.
 4. The method according toclaim 1, wherein the second entity is a cellular network provider or acable network provider.
 5. The method according to claim 1, furthercomprising: determining a confidence level of (i) the first deviceidentification information and (ii) the second device identificationinformation match.
 6. The method according to claim 1, wherein the firstdevice identification information and the second device identificationinformation is at least one of a telephone number, a device serialnumber, a unique serial number (ICCID), an international mobilesubscriber identity (IMSI) number, or an International Mobile EquipmentIdentity (IMEI).
 7. The method according to claim 1, further comprising:receiving a first set of biometric data from the first entity, the firstset of biometric data used at log in at the first entity; receiving asecond set of biometric data from the second entity, the second set ofbiometric data used when accessing the network address; and performing acomparison between the first set of biometric data and the second set ofbiometric data.
 8. An apparatus for performing frictionless two-factorauthentication, the apparatus comprising at least one processor and atleast one memory including computer program code, the at least onememory and the computer program code configured to, with the processor,cause the apparatus to at least: receive, from a first entity, anindication of a request received at the first entity to access anaccount from a device associated with a user, the indication comprisingat least one instance of first device identification information of atleast one device having authorization to access the account; provide anetwork address to the first entity, the network address configured tobe sent to the device from the first entity; receive, from a secondentity, second device identification information, the second deviceidentification information determined upon the device accessing to thenetwork address; normalize the first device identification informationand the second device identification information; perform a real-timecomparison between the first device identification information andsecond device identification information, wherein the real-timecomparison between the first device identification information andsecond device identification information comprises determining whether(i) the normalized first device identification information and (ii) thenormalized second device identification information match; and promptthe first entity to grant the device access to the account if a match isdetected between the normalized first device identification informationand the normalized second device identification information.
 9. Theapparatus according to claim 8, wherein the network address is a uniformresource locator (URL) address.
 10. The apparatus according to claim 8,wherein the first entity is a bank server.
 11. The apparatus accordingto claim 8, wherein the second entity is a cellular network provider ora cable network provider.
 12. The apparatus according to claim 8,wherein the at least one memory and the computer program code arefurther configured to, with the processor, cause the apparatus to:determine a confidence level of (i) the first device identificationinformation and (ii) the second device identification information match.13. The apparatus according to claim 8, wherein the first deviceidentification information and the second device identificationinformation is at least one of a telephone number, a device serialnumber, a unique serial number (ICCID), an international mobilesubscriber identity (IMSI) number, or an International Mobile EquipmentIdentity (IMEI).
 14. The apparatus according to claim 8, wherein the atleast one memory and the computer program code are further configuredto, with the processor, cause the apparatus to: receive a first set ofbiometric data from the first entity, the first set of biometric dataused at log in at the first entity; receive a second set of biometricdata from the second entity, the second set of biometric data used whenaccessing the network address; and performing a comparison between thefirst set of biometric data and the second set of biometric data.
 15. Acomputer program product for performing frictionless two-factorauthentication, the computer program product comprising at least onenon-transitory computer-readable storage medium havingcomputer-executable program code instructions stored therein, thecomputer-executable program code instructions comprising program codeinstructions for: receiving, from a first entity, an indication of arequest received at the first entity to access an account from a deviceassociated with a user, the indication comprising at least one instanceof first device identification information of at least one device havingauthorization to access the account; providing a network address to thefirst entity, the network address configured to be sent to the devicefrom the first entity; receiving, from a second entity, second deviceidentification information, the second device identification informationdetermined upon the device accessing to the network address; normalizingthe first device identification information and the second deviceidentification information; performing a real-time comparison betweenthe first device identification information and second deviceidentification information, wherein the real-time comparison between thefirst device identification information and second device identificationinformation comprises determining whether (i) the normalized firstdevice identification information and (ii) the normalized second deviceidentification information match; and prompting the first entity togrant the device access to the account if a match is detected betweenthe normalized first device identification information and thenormalized second device identification information.
 16. The computerprogram product according to claim 15, wherein the network address is auniform resource locator (URL) address.
 17. The computer program productaccording to claim 15, wherein the first entity is a bank server. 18.The computer program product according to claim 15, wherein the secondentity is a cellular network provider or a cable network provider. 19.The computer program product according to claim 15, wherein thecomputer-executable program code instructions further comprise programcode instructions for: determining a confidence level of (i) the firstdevice identification information and (ii) the second deviceidentification information match.
 20. The computer program productaccording to claim 15, wherein the first device identificationinformation and the second device identification information is at leastone of a telephone number, a device serial number, a unique serialnumber (ICCID), an international mobile subscriber identity (IMSI)number, or an International Mobile Equipment Identity (IMEI).
 21. Thecomputer program product according to claim 15, wherein thecomputer-executable program code instructions further comprise programcode instructions for: receiving a first set of biometric data from thefirst entity, the first set of biometric data used at log in at thefirst entity; receiving a second set of biometric data from the secondentity, the second set of biometric data used when accessing the networkaddress; and performing a comparison between the first set of biometricdata and the second set of biometric data.
 22. A method for performingfrictionless two-factor authentication, the method comprising:receiving, from a first entity, an indication of a request received atthe first entity to access an account from a device associated with auser, the indication comprising at least one instance of first deviceidentification information of at least one device having authorizationto access the account; providing a network address to the first entity,the network address configured to be sent to the device from the firstentity; receiving, from a second entity, second device identificationinformation, the second device identification information determinedupon the device accessing to the network address; receiving a first setof biometric data from the first entity, the first set of biometric dataused at log in at the first entity; receiving a second set of biometricdata from the second entity, the second set of biometric data used whenaccessing the network address; performing a real-time comparison betweenthe first device identification information and second deviceidentification information; performing a comparison between the firstset of biometric data and the second set of biometric data; andprompting the first entity to grant the device access to the account ifa match is detected between both (i) the first device identificationinformation and the second device identification information and (ii)the first set of biometric data and the second set of biometric data.23. An apparatus for performing frictionless two-factor authentication,the apparatus comprising at least one processor and at least one memoryincluding computer program code, the at least one memory and thecomputer program code configured to, with the processor, cause theapparatus to at least: receive, from a first entity, an indication of arequest received at the first entity to access an account from a deviceassociated with a user, the indication comprising at least one instanceof first device identification information of at least one device havingauthorization to access the account; provide a network address to thefirst entity, the network address configured to be sent to the devicefrom the first entity; receive, from a second entity, second deviceidentification information, the second device identification informationdetermined upon the device accessing to the network address; receive afirst set of biometric data from the first entity, the first set ofbiometric data used at log in at the first entity; receive a second setof biometric data from the second entity, the second set of biometricdata used when accessing the network address; perform a real-timecomparison between the first device identification information andsecond device identification information; perform a comparison betweenthe first set of biometric data and the second set of biometric data;and prompt the first entity to grant the device access to the account ifa match is detected between both (i) the first device identificationinformation and the second device identification information and (ii)the first set of biometric data and the second set of biometric data.24. A computer program product for performing frictionless two-factorauthentication, the computer program product comprising at least onenon-transitory computer-readable storage medium havingcomputer-executable program code instructions stored therein, thecomputer-executable program code instructions comprising program codeinstructions for: receiving, from a first entity, an indication of arequest received at the first entity to access an account from a deviceassociated with a user, the indication comprising at least one instanceof first device identification information of at least one device havingauthorization to access the account; providing a network address to thefirst entity, the network address configured to be sent to the devicefrom the first entity; receiving, from a second entity, second deviceidentification information, the second device identification informationdetermined upon the device accessing to the network address; receiving afirst set of biometric data from the first entity, the first set ofbiometric data used at log in at the first entity; receiving a secondset of biometric data from the second entity, the second set ofbiometric data used when accessing the network address; performing areal-time comparison between the first device identification informationand second device identification information; performing a comparisonbetween the first set of biometric data and the second set of biometricdata; and prompting the first entity to grant the device access to theaccount if a match is detected between both (i) the first deviceidentification information and the second device identificationinformation and (ii) the first set of biometric data and the second setof biometric data.